Grow the walkthrough to ten steps and fold Full Example into it - #173

Full Example was a step-by-step tutorial living outside the tutorial. It
is now inside it: the two things it taught that the walkthrough did not
became steps of their own, and the page is gone.

  Step 8  Selection Screen - a SimpleForm with DatePickers over the
          list, a Read button, and the SELECT the reader would write in
          their own system as the comment above the demo data
  Step 9  Tables - sap.m.List becomes sap.m.Table: columns, cells, the
          end( ) that makes the next Column a sibling, and a row action
          in a 10%-wide column of its own
  Step 10 App Structure - what was step 8, now assembling all of it:
          dispatcher, named methods, data_read / data_update as the only
          places a SELECT or an UPDATE appears, and the back button

One overview page, not two. The walkthrough's Introduction folded into
the Tutorial overview - a section whose landing page is followed by a
second landing page makes the reader click twice to reach step 1.

Hello World gains a second example rather than losing its content: the
message-box class, then a class with a view, a bound input and an event -
the whole shape of an app on one page - and the developer tools, which
are too useful to be three clicks away. What it does NOT do any more is
explain all of it; that is what the walkthrough is for, and the page says
so and links there.

Also, from reading it over:

  - Tutorials -> Tutorial in the nav and the sidebar
  - step 1 is "The App Class"; "Hello World" was standing twice, once
    per section, meaning two different things
  - the Walkthrough group has no `collapsed` key at all, like Quickstart:
    that is what makes a group a plain list rather than a foldable one
  - Getting Started's "Introduction" is "In a Nutshell" - the page is an
    elevator pitch with a Hello World in it, not a preface
  - Tooling moves to Advanced Topics > Developer Setup. Which editor and
    client tooling you develop WITH is not a question a newcomer has yet

The AI page is rewritten from the other end. It opened by explaining
what a model gets wrong; it now opens with why abap2UI5 suits an agent in
the first place - one class and no generated services, an app that is
text end to end, hundreds of tested samples to copy from, and a linter
that verifies the result with no SAP system. The frozen-builder framing
is out of the page, prompt included.

Verified in a playground built from source: all ten steps and both Hello
World classes carry a Run button, all ten start and render, and the
behaviour each page promises was driven - the toast, the bound greeting,
the five rows, the row-specific event, the supplier filter reaching the
read, the table's four headers and its row action, the dialog editing
the clicked row, Save updating the table and Cancel leaving it alone.
The preview image is the finished app, recaptured. Gates green in both
repositories; the samples pairing holds in both directions (47 pages,
118 links).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PwxPfiy5WE8fVxfnToFeWk